adding-instance-restarts-changelog-entry #26372
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rita3ko
requested changes
Nov 10, 2025
| @@ -0,0 +1,21 @@ | |||
| --- | |||
| title: Instance restarts now supported in Workflows | |||
| description: You can now restart an instance of your workflow without losing its concurrency spot | |||
| await instance.restart(); // Returns Promise<void> | ||
| ``` | ||
|
|
||
| You may want to [restart an instance](/workflows/build/trigger-workflows/#restart-a-workflow) if the Workflow has been updated, the parameters have changed, or the Workflow has reached its step limit. Restarting an instance will immediately cancel any in-progress steps, erase any intermediate state, and treat the Workflow as if it was run for the first time. |
Collaborator
There was a problem hiding this comment.
Would be good to add a sentence here of why this is important
|
|
||
| You may want to [restart an instance](/workflows/build/trigger-workflows/#restart-a-workflow) if the Workflow has been updated, the parameters have changed, or the Workflow has reached its step limit. Restarting an instance will immediately cancel any in-progress steps, erase any intermediate state, and treat the Workflow as if it was run for the first time. | ||
|
|
||
| If the instance is already running, the restart will not lose its concurrency slot (limit of 10,000 concurrent instances). However, the restarted instance will count towards the creation rate limit (100 instances per second). |
Collaborator
There was a problem hiding this comment.
this is a bit confusing to parse. i would clarify concurrency vs. creation here a bit more. i.e. does this help if i have 10,001 instances? or is this useful in general?
what does creation mean here?
Maddy-Cloudflare
approved these changes
Nov 13, 2025
rita3ko
reviewed
Nov 13, 2025
|
|
||
| If the instance is already running, the restart will not lose its concurrency slot (limit of 10,000 concurrent instances). For example, say you have 10,000 instances running and 2,000 instances queued. If you restart a runnning instance, it will maintain its spot in the 10,000 rather than slotting into the back of the queue. | ||
|
|
||
| However, note that the restarted instance will count towards the instance creation rate limit (100 Workflow instances per second). |
Collaborator
There was a problem hiding this comment.
I would drop this line. I think it adds more questions than it answers (assuming this is documented)
rita3ko
reviewed
Nov 13, 2025
|
|
||
| You may want to [restart an instance](/workflows/build/trigger-workflows/#restart-a-workflow) if the Workflow has been updated, the parameters have changed, or the Workflow has reached its step limit. This allows you to make changes without waiting until the instance is complete or preserve a long-running instance through restart. Restarting an instance will immediately cancel any in-progress steps, erase any intermediate state, and treat the Workflow as if it was run for the first time. | ||
|
|
||
| If the instance is already running, the restart will not lose its concurrency slot (limit of 10,000 concurrent instances). For example, say you have 10,000 instances running and 2,000 instances queued. If you restart a runnning instance, it will maintain its spot in the 10,000 rather than slotting into the back of the queue. |
Collaborator
There was a problem hiding this comment.
I like the example. You can be more concrete — and say if the instance was in the 300th slot, it would go back in there as opposed to the 2001st.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adding changelog for instance.restart() support in Cloudflare Workflows